Discovery of asset information through scanning of communication tags associated with assets

ABSTRACT

In some embodiments, a mobile device includes an interface configured to scan information from a communication tag associated with an asset, a memory operable to store the information, and a processor communicatively coupled to the memory. The information comprises a header describing the information, business application data, and asset identification data uniquely identifying the asset. The processor is configured to extract the business application data from the information scanned from the communication tag and extract the asset identification data from the information scanned from the communication tag.

TECHNICAL FIELD

The present disclosure relates to asset management and more specificallyto discovery of asset information through scanning of communication tagsassociated with assets.

BACKGROUND

Asset management may refer to systems whereby items of value to anentity or group are monitored and/or maintained. Asset management mayapply to both tangible and intangible concepts. Asset management mayinclude a systematic process of operating, maintaining, and upgradingassets cost-effectively. Asset management may also include the practiceof managing assets so that the greatest return is achieved.

SUMMARY

In some embodiments, a mobile device includes an interface configured toscan information from a communication tag associated with an asset, amemory operable to store the information, and a processorcommunicatively coupled to the memory. The information comprises aheader describing the information, business application data, and assetidentification data uniquely identifying the asset. The processor isconfigured to extract the business application data from the informationscanned from the communication tag and extract the asset identificationdata from the information scanned from the communication tag.

Certain embodiments may provide one or more technical advantages. Atechnical advantage of one embodiment may include the capability totrack assets within an enterprise using existing procedures forreceiving and processing data for business applications. A technicaladvantage of one embodiment may include the capability to provide acommunication tag storing both asset data uniquely identifying an assetand business application data serving a business purpose unrelated tothe asset. A technical advantage of one embodiment may include thecapability to generate and process communication tags while gatheringinformation about the assets that generated those communication tags.

Various embodiments of the invention may include none, some, or all ofthe above technical advantages. One or more other technical advantagesmay be readily apparent to one skilled in the art from the figures,descriptions, and claims included herein.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and itsadvantages, reference is now made to the following description taken inconjunction with the accompanying drawings, in which:

FIG. 1 shows an asset management system according to one embodiment;

FIG. 2 shows the information, mobile device data, and augmented data ofFIG. 1 according to one example embodiment; and

FIG. 3 shows a method for generating, scanning, and processingcommunication tags.

DETAILED DESCRIPTION

Business applications may receive, process, and/or transmit businessdata for a variety of different purposes. In one example, an informationtechnology (IT) service desk may use a business application to manageservice tickets. In this example, the business application may trackservice ticket identifiers associated with service tickets. Each serviceticket identifier may identify a certain service ticket, and a databasemay store information associated with each service ticket identifier(e.g., a completion status for each service ticket identifier). Uponreceiving a service ticket identifier, the business application mayretrieve and/or update information associated with the service ticket(e.g., update the database to indicate that the service ticket iscomplete).

In this example, a user may be required to input the service ticketidentifier into the business application. In some scenarios, the usermay input the service ticket identifier manually using a keyboard. Inother scenarios, other communication mechanisms may be used to increasethe speed at which business data is input into the business application.For example, a barcode may be printed on the service ticket. A barcodeis an optical machine-readable representation of data. The barcode maystore the service ticket identifier, and the service ticket identifierinput into the business application by presenting the service ticket toa bar code reader that scans the barcode.

Printing bar codes on service tickets, however, requires a printer. Fora large company, many printers may be deployed throughout the company.Managing these printers creates a new set of logistical problems. Forexample, the company may wish to know how many printers are in service,how often the printers are used, where the printers are located, or whois using the printers. For a large company, however, obtaining thisinformation may be cost-prohibitive because the information is noteasily obtainable. For example, if a printer is moved, personnel may berequired to search for and locate the new location of the printer andthen update that location in a database. In another example, personnelmay be required to visually inspect and record page counts on eachprinter, which can be quite time-consuming for large companies.

To summarize, business applications may receive business applicationdata (e.g., service ticket identifiers) generated using business assets(e.g., printers), but tracking and managing these business assets may becostly. Teachings of certain embodiments provide the capability to trackand manage the business assets using the procedures for receivingbusiness application data. Returning to the previous example, teachingsof certain embodiments provide the capability to track and manageprinters through the scanning of service ticket identifiers. Byutilizing a business procedure already in place (scanning of serviceticket identifiers), the company may track assets (e.g., printers)without requiring additional steps to be taken by personnel.

In some example embodiments, asset data is included in the business datato be scanned. Returning to the previous example, the barcode maytheoretically include the service ticket identifier as well asinformation uniquely identifying the asset that generated the barcode(e.g., a serial number of the printer), other information regarding theasset (e.g., printer model), and information regarding printing of thebarcode (e.g., time of printing, identification of user who printedbarcode).

A standard one-dimensional barcode, however, has a limited storagecapacity and may not be able to include all this information.Accordingly, teachings of certain embodiments provide the capability ofusing higher-volume representations of data, such as two-dimensionalQuick Response (QR) codes, to store both business application data andasset data. Thus, QRCodes may be printed by company personnel for onepurpose (e.g., printing service tickets), but the QRCodes may also beused for an entirely different purpose (e.g., tracking and managingprinters).

In these examples, the business application data may not have anyassociation with the asset that generated the QRCode. Returning to theprevious example, a service ticket printed on a printer may not have anyrelation to the printer itself, and the service ticket identifier maynot identify the printer in any way. The asset data included in theQRCode, however, may uniquely identify the printer and provideadditional information about the printer.

Some information may be learned about the printer through the act ofscanning the QRCode. For example, the printer may not know its ownlocation, and thus this information may not necessarily be included inthe QRCode. A device used for scanning, however, may know its location,and the location of the device for scanning may be used to approximatethe location of the printer. For example, the device for scanning may bea mobile device equipped with a global positioning system (GPS) locationtracker. In this example, the mobile device may insert the locationidentified by the GPS location tracker into the asset data received fromthe QRCode. In other words, the mobile device may augment the asset datawith information associated with the mobile device.

FIG. 1 shows an asset management system 100 according to one embodiment.The asset management system 100 of FIG. 1 features a mobile device 10,an asset 30, a communication tag 32, a location network 40, a datanetwork 50, and a data center 60. In operation, a user 5 may interactwith mobile device 10 to scan information from communication tag 32 andtransmit information to data center 60. Although the example of FIG. 1shows one mobile device 10, one asset 30, one location network 40, onedata network 50, and one data center 60, embodiments of system 100 mayinclude more or fewer mobile devices 10, assets 30, location networks40, data networks 50, and/or data centers 60.

Users 5 may include any individual, group of individuals, and/or entitythat interacts with mobile device 10. Examples of users 5 include, butare not limited to, an employee, manager, executive, accountant,engineer, technician, contractor, agent, and/or customer. Users 5 may beassociated with a business or other organization.

Mobile device 10 may include processors 12, input/output devices 14,communications links 16, and memory 18. In other embodiments, mobiledevice 10 may include more, less, or other components. Mobile device 10may be operable to perform one or more operations of variousembodiments. Examples of a mobile device may include, but are notlimited to, mobile telephones (e.g., feature phones and smart phones),personal digital assistants (PDA), and mobile computers (e.g., tabletand netbook).

Processors 12 represent one or more tangible hardware devices operableto execute logic contained within a medium. In particular embodiments,processor 12 includes hardware for executing instructions, such as thosemaking up a computer program. As an example and not by way oflimitation, to execute instructions, processor 12 may retrieve (orfetch) the instructions from an internal register, an internal cache, ormemory 18; decode and execute them; and then write one or more resultsto an internal register, an internal cache, or memory 18. In particularembodiments, processor 12 may include one or more internal caches fordata, instructions, or addresses. This disclosure contemplates processor12 including any suitable number of any suitable internal caches, whereappropriate. As an example and not by way of limitation, processor 12may include one or more instruction caches, one or more data caches, andone or more translation lookaside buffers (TLBs). Instructions in theinstruction caches may be copies of instructions in memory 18, and theinstruction caches may speed up retrieval of those instructions byprocessor 12. Data in the data caches may be copies of data in memory 18for instructions executing at processor 12 to operate on; the results ofprevious instructions executed at processor 12 for access by subsequentinstructions executing at processor 12 or for writing to memory 18; orother suitable data. The data caches may speed up read or writeoperations by processor 12. The TLBs may speed up virtual-addresstranslation for processor 12. In particular embodiments, processor 12may include one or more internal registers for data, instructions, oraddresses. This disclosure contemplates processor 12 including anysuitable number of any suitable internal registers, where appropriate.Where appropriate, processor 12 may include one or more arithmetic logicunits (ALUs); be a multi-core processor; or include one or moreprocessors 12. Although this disclosure describes and illustrates aparticular processor, this disclosure contemplates any suitableprocessor.

Input/output devices 14 may include any device or interface operable toenable communication between mobile device 10 and external components,including communication with a user or another system. Exampleinput/output devices 14 may include, but are not limited to, a display,keyboard, touch screen, camera, and microphone. Input/output devices 14may be external to or internal to mobile device 10. For example,input/output devices 14 may include both a built-in keyboard, a plug-inkeyboard, and a wireless keyboard.

Interfaces 16 are operable to facilitate communication between mobiledevice 10 and another element of a network. Interfaces 16 may connect toany number and combination of wireline and/or wireless networks suitablefor data transmission, including transmission of communications.Interfaces 16 may, for example, communicate audio and/or video signals,messages, internet protocol packets, frame relay frames, asynchronoustransfer mode cells, and/or other suitable data between networkaddresses. Interfaces 16 connect to a computer network or a variety ofother communicative platforms including, but not limited to, a wirelessnetwork, a cellular network, a public switched telephone network (PSTN);a public or private data network; one or more intranets; a local areanetwork (LAN); a metropolitan area network (MAN); a wide area network(WAN); a local, regional, or global communication network; an opticalnetwork; a satellite network; a cellular network; an enterpriseintranet; all or a portion of the Internet; other suitable interfaces;or any combination of the preceding.

In the example of FIG. 1, mobile device 10 includes three interfaces 16a, 16 b, and 16 c. Interface 16 a is a network interface that connectsto network 50, allowing mobile device 10 to send and receive informationwith data center 60. Interface 16 b is an asset interface thatcommunicates with communication tag 32, such as by scanning informationfrom communication tag 32. In some example embodiments, mobile device 30scans information from communication tag 32 through interface 16 b usingQRCode scanning or near-field communication. Interface 16 c connects tolocation network 40. In one example embodiment, interface 16 c is aglobal positioning system receiver that receives location signals fromsatellites within location network 40.

Memory 18 represents any suitable storage mechanism and may store anydata for use by mobile device 10. Memory 18 may comprise one or moretangible, computer-readable, and/or computer-executable storage medium.Examples of memory 18 include computer memory (for example, RandomAccess Memory (RAM) or Read Only Memory (ROM)), mass storage media (forexample, a hard disk), removable storage media (for example, a memorydisk or smart card), database and/or network storage (for example, aserver), and/or other computer-readable medium.

In some embodiments, memory 18 stores logic 20. Logic 20 facilitatesoperation of mobile device 10. Logic 20 may include hardware, software,and/or other logic. Logic 20 may be encoded in one or more tangible,non-transitory media and may perform operations when executed by acomputer. Logic 20 may include a computer program, software, computerexecutable instructions, and/or instructions capable of being executedby mobile device 10. Example logic 20 may include any of the well-knownmobile-device operating systems, such as Blackberry OS, BlackberryTablet OS, Google Android, Windows Phone, webOS, Symbian OS, Apple iOS,and Samsung's Bada, as well as other operating systems such as OS2,UNIX, Mac-OS, Linux, and Windows Operating Systems or other operatingsystems. In particular embodiments, the operations of the embodimentsmay be performed by one or more computer readable media storing,embodied with, and/or encoded with a computer program and/or having astored and/or an encoded computer program. Logic 20 may also be embeddedwithin any other suitable medium without departing from the scope of theinvention.

In the example of FIG. 1, logic 20 may include a mobile assetapplication 22. Mobile asset application 22 receives information 24 fromcommunication tag 32 and mobile device data 26 from mobile device 10 andgenerates augmented data 28.

In some embodiments, information 24 includes a header, businessapplication data, and asset data. The header describes information 24.For example, the header may describe the format and version ofcommunication tag 32. In addition, the header may describe where thebusiness application data and the asset data are located withininformation 24. The header may also describe when communication tag 32was created.

The business application data includes information for use in a businessapplication and may serve some business purpose (e.g., tracking servicetickets). The business application data may not have any associationwith asset 30.

The asset data uniquely identifies asset 30. The asset data may alsoinclude other information regarding the asset (e.g., asset model) andinformation regarding generation of communication tag 32 (e.g., time ofgeneration, identification of user who generated communication tag 32).

In some embodiments, the asset data is expressed in the form of auniform resource locator (URL). By accessing the URL, the asset datacontained within information 24 may be latently communicated to assetmanager 70. In addition, URLs may provide a flexible and dynamic formatfor encoding asset information because URLs are interpreted on theserver side when called. URLs may also provide a standardized means formobile asset application 22 to augment the asset data with mobile devicedata 26. Mobile asset application 22 may augment the asset data byadding parameters from mobile device data 26 to the URL.

Mobile device data 26 is data associated with mobile device 10. Examplesof mobile device data 26 may include, but are not limited to,identification of mobile device 10, identification of a user of mobiledevice 10, a location of mobile device 10, and the time at which mobiledevice 10 scans communication tag 32. In one example, mobile device data26 includes location information retrieved from location network 40through location interface 16 c. Mobile asset application 22 may augmentinformation 24 with mobile device data 26 to yield augmented data 28.For example, mobile asset application 22 may insert mobile device data26 into the asset data to yield augmented data 28.

In the example of FIG. 1, logic 20 also includes a business application80. Business application 80 may receive and/or process the businessapplication data from information 24. For example, business application80 may receive the business application data and update a database ofinformation in light of the business application data. If, for example,the business application data is inventory information regarding aparticular product, business application 80 may update an inventorytracking database in light of the business application data.

Asset 30 may include any item to be tracked and/or managed. In someembodiments, asset 30 generates communication tag 32. Examples of asset30 may include, but are not limited to, electronics equipment such as acomputer, monitor, printer, or networking device. For example, acomputer may render a communication tag 32 on a monitor, which may bescanned by mobile device 10. In another example, a printer may print acommunication tag 32 onto an object such as a piece of paper. In thisexamples, asset 30 may not be the originator of the content withincommunication tag 32. For example, a printer may print content generatedfrom a computer, and that computer may receive the content from anothercomputer.

Communication tag 32 communicates information 24 to mobile device 10. Inone example embodiment, communication tag 32 is a two-dimensionalbarcode, such as a QRCode. A QRCode is a two-dimensional bar-code thatcan be scanned by any of a variety of devices capable of opticalrecognition, such as purpose built scanners, computers or smart phonesconnected to or comprising a camera. In situations in which the QRCodeis being scanned by a smart phone, the contents of the QRCode may beinterpreted by a mobile application running on the smart phone. In somescenarios, based on the content of the QRCode, the device scanning theQRCode can navigate to an URL embedded in the QRCode to access contentincluding but not limited to media files. The QRCode may also directlydownload or present the media files without navigating to a URL. In someembodiments, the QRCodes may be used to initiate contact (e.g., email,phone, text, instant message, etc.) with a company representative or toload an application provided by the company.

In another example embodiment, communication tag 32 is a near-fieldcommunication (NFC) device. NFC is a wireless technology that is used toexchange data between devices in very close proximity (2″ or less). LikeQRCodes, NFC may be capable of transmitting both business applicationdata and asset data.

Location network 40 may include any communication devices operable toprovide location information to mobile device 10. One example oflocation network 40 may include satellites that provide globalpositioning information to mobile device 10. Another example of locationnetwork 40 may include a local positioning system with elements such ascellular base stations, Wi-Fi access points, trace networks (e.g.,“fingerprinting), and radio broadcast towers. Interface 16 c may use anysuitable method for determining the location of mobile device 10 usingsignals received from location network 40, such as triangulation andtrilateration.

Network 50 may represent any number and combination of wireline and/orwireless networks suitable for data transmission. Network 50 may, forexample, communicate internet protocol packets, frame relay frames,asynchronous transfer mode cells, and/or other suitable data betweennetwork addresses. In the example of FIG. 1, Network 50 is a cellulardata network. In some embodiments, however, Network 50 may include anypublic or private data network; one or more intranets; a local areanetwork (LAN); a metropolitan area network (MAN); a wide area network(WAN); a wireline or wireless network; a local, regional, or globalcommunication network; an optical network; a satellite network; acellular network; an enterprise intranet; all or a portion of theInternet; other suitable interfaces; or any combination of thepreceding. Although the illustrated embodiment shows one network 50,certain embodiments recognize that more or fewer networks may be usedand that not all elements may communicate via a network. Certainembodiments also recognize that communications over a network is oneexample of a mechanism for communicating between parties, and anysuitable mechanism may be used.

Data center 60 receives business application data, asset data, and/ormobile device data from mobile device 10. In one example embodiment,data center 60 receives augmented data 28, which includes both assetdata and mobile device data.

Data center 60 may include processors 62, input/output devices 64,communications links 66, and memory 68. In other embodiments, datacenter 60 may include more, less, or other components. Data center 60may be operable to perform one or more operations of variousembodiments. Although the embodiment shown provides one example of datacenter 60 that may be used with other embodiments, such otherembodiments may utilize computers other than data center 60.Additionally, embodiments may also employ multiple data centers 60 orother computers networked together in one or more public and/or privatecomputer networks, such as one or more networks 30. For example, in someembodiments, asset manager 70 and business application 70 may beassociated with different data centers 60.

Processors 62 represent one or more tangible hardware devices operableto execute logic contained within a medium. In particular embodiments,processor 62 includes hardware for executing instructions, such as thosemaking up a computer program. As an example and not by way oflimitation, to execute instructions, processor 62 may retrieve (orfetch) the instructions from an internal register, an internal cache, ormemory 68; decode and execute them; and then write one or more resultsto an internal register, an internal cache, or memory 68. In particularembodiments, processor 62 may include one or more internal caches fordata, instructions, or addresses. This disclosure contemplates processor62 including any suitable number of any suitable internal caches, whereappropriate. As an example and not by way of limitation, processor 62may include one or more instruction caches, one or more data caches, andone or more translation lookaside buffers (TLBs). Instructions in theinstruction caches may be copies of instructions in memory 68, and theinstruction caches may speed up retrieval of those instructions byprocessor 62. Data in the data caches may be copies of data in memory 68for instructions executing at processor 62 to operate on; the results ofprevious instructions executed at processor 62 for access by subsequentinstructions executing at processor 62 or for writing to memory 68; orother suitable data. The data caches may speed up read or writeoperations by processor 62. The TLBs may speed up virtual-addresstranslation for processor 62. In particular embodiments, processor 62may include one or more internal registers for data, instructions, oraddresses. This disclosure contemplates processor 62 including anysuitable number of any suitable internal registers, where appropriate.Where appropriate, processor 62 may include one or more arithmetic logicunits (ALUs); be a multi-core processor; or include one or moreprocessors 62. Although this disclosure describes and illustrates aparticular processor, this disclosure contemplates any suitableprocessor.

Input/output devices 64 may include any device or interface operable toenable communication between data center 60 and external components,including communication with a user or another system. Exampleinput/output devices 64 may include, but are not limited to, a mouse,keyboard, display, and printer.

Interfaces 66 are operable to facilitate communication between datacenter 60 and another element of a network, such as other data centers60. Interfaces 66 may connect to any number and combination of wirelineand/or wireless networks suitable for data transmission, includingtransmission of communications. Interfaces 66 may, for example,communicate audio and/or video signals, messages, internet protocolpackets, frame relay frames, asynchronous transfer mode cells, and/orother suitable data between network addresses. Interfaces 66 connect toa computer network or a variety of other communicative platformsincluding, but not limited to, a public switched telephone network(PSTN); a public or private data network; one or more intranets; a localarea network (LAN); a metropolitan area network (MAN); a wide areanetwork (WAN); a wireline or wireless network; a local, regional, orglobal communication network; an optical network; a satellite network; acellular network; an enterprise intranet; all or a portion of theInternet; other suitable interfaces; or any combination of thepreceding.

Memory 68 represents any suitable storage mechanism and may store anydata for use by data center 60. Memory 68 may comprise one or moretangible, computer-readable, and/or computer-executable storage medium.Examples of memory 68 include computer memory (for example, RandomAccess Memory (RAM) or Read Only Memory (ROM)), mass storage media (forexample, a hard disk), removable storage media (for example, a CompactDisk (CD) or a Digital Video Disk (DVD)), database and/or networkstorage (for example, a server), and/or other computer-readable medium.

In some embodiments, memory 68 stores asset manager 70. Asset manager 70tracks and manages assets 30. Asset manager 70 may manage informationgathered when mobile device 10 scans communication tag 32. For example,asset manager 70 may be able to identify an asset 30, the model andcharacteristics of asset 30, where asset 30 is located, when asset 30was last used, who has been using asset 30, when asset 30 has generatedcommunication tags 32, and when those communication tags 32 werescanned. Asset manager 70 may also provide additional information basedon information gathered when mobile device 10 scans communication tag32. For example, asset manager 70 may calculate the workload or lifeexpectancy of asset 30 based on the totality of scans of communicationtags 32. As another example, asset manager 70 may be able to track themovement of asset 30 throughout a company and identify where additionalassets 30 may be useful.

Memory 68 may also stores business application 80. In some embodiments,business application 80 performs similar functions to the businessapplication 80 of mobile device 10. In these embodiments, businessapplication 80 may be located on mobile device 10, data center 60, orboth locations. In some embodiments, business applications 80 on mobiledevice 10 and data center 60 work together. For example, businessapplication 80 on mobile device 10 may process information into a formsuitable to the business application 80 on data center 60.

In operation, according to one example embodiment, asset 30 is a printerthat prints communication tag 32 on a service ticket. In this exampleembodiment, communication tag 32 stores information 24, which includes aheader, business application data, and asset data. The header mayidentify information such as the date communication tag 32 was generatedand the length of the business application data (e.g., 000A, or 10characters). The business application data includes an identifier thatidentifies the service ticket. The asset data includes informationuniquely identifying the printer.

In this example embodiment, asset interface 16 b of mobile device 10scans communication tag 32 for information 24. Mobile asset application22 provides the business application data to business application 80,which runs locally on mobile device 10 and/or remotely on data center60. Mobile asset application 22 also augments the asset data with mobiledevice data 26 to yield augmented data 28. For example, mobile assetapplication 22 may insert mobile device data 26 such as locationinformation, time of scan information, and information identifying themobile device 10 into the asset data to yield augmented data 28.

FIG. 2 shows information 24, mobile device data 26, and augmented data28 according to one example embodiment. In the example of FIG. 2,information 24 includes a header, business application data, and assetdata. The header describes information 24. For example, the header maydescribe where the business application data and the asset data arelocated within information 24. The business application data includesinformation for use in a business application and may serve somebusiness purpose (e.g., tracking service tickets). The businessapplication data may not have any association with asset 30. The assetdata uniquely identifies asset 30. The asset data may also include otherinformation regarding the asset (e.g., asset model) and informationregarding generation of communication tag 32 (e.g., time of generation,identification of user who generated communication tag 32). In someembodiments, some of this information may be included in the headerrather than the asset data. For example, the time at which communicationtag 32 is generated may be located in the header rather than the assetdata.

Mobile device data 26 is data associated with mobile device 10. Examplesof mobile device data 26 may include, but are not limited to,identification of mobile device 10, identification of a user of mobiledevice 10, a location of mobile device 10, and the time at which mobiledevice 10 scans communication tag 32. In one example, mobile device data26 includes location information retrieved from location network 40through location interface 16 c.

In the example of FIG. 2, the business application data found ininformation 24 is transmitted to business application 80. The assetdata, as well as some data from the header, are combined with the mobiledevice data 26 to yield augmented data 28. Some example scenarios areprovided below to explain this process in greater detail.

In a first example scenario, asset 30 is a printer that prints a QRCode(communication tag 32) on a service ticket. In this example scenario,information 24 includes:

[HEADER]

A—QRCode Format

1—Version

3BE2 (15330)—Days since EPOC 1970

000A (10)—Length of application data

[APPLICATION DATA]

SD:12210730

[ASSET DATA]

http://xxx.yy/1?assetID=3828202—The asset information URL

In this example, the fully encoded QR Packet would appear as so:

A113BE2000ASD:12210730http://xxx.yy/1?assetID-3828202

When mobile asset application 22 provides the business application datato business application 80, which runs locally on mobile device 10and/or remotely on data center 60. Mobile asset application 22 alsoaugments the asset data with mobile device data 26 to yield augmenteddata 28. For example, mobile asset application 22 may insert mobiledevice data 26 such as location information, time of scan information,and information identifying the mobile device 10 into the asset data toyield augmented data 28. For example, mobile asset application 22 mayaugment the asset data with the mobile device data 26 to yield thefollowing augmented data 28:

http://xxx.yy/1?assetID=3828202& when=3BE2& latitude=38.234231&longitude=34.234232& altitude=510& userId=user-1@xxx.yy&scanTime=1307126406& deviceString=Android2.3

Once augmented data 28 is generated, the augmented URL may be accessedby mobile device 10 and/or data center 60. In some embodiments,accessing the augmented URL will report information about asset 30 toasset manager 70. For example, the endpoint for the URL may decode theURL and enter the asset information into asset manager 70. As a resultof this process, asset manager 70 may learn information such as: (1)whether the printer is still being used, (2) approximate location forthe printer, (3) traceability between printers and service tickets, and(4) information about who is using the printer.

In a second example scenario, asset 30 is a monitor that displays aQRCode (communication tag 32) on a computer screen for purposes ofauthenticating a user. For example, a user may log-in to an applicationthrough a website, and the user may scan the QRCode on the website aspart of a process for logging-in. The asset information may be encodedin the QRCode either by the browser (using a client-side QRCodegeneration library) on the server side (which examines the incoming HTTPrequest). In this example scenario, information 24 includes:

[HEADER]

A—QRCode Format

1—Version

3BD9 (15327)—Days since EPOC 1970

004c (76)—Length of application data

[APPLICATION DATA]

175619882ef8485799f163bc906eddd562c02bc48975cfc1247 . . .

[ASSET DATA]

http://xxx.yy/1?ip=17.29.42.137&os=0.1&osv=SP3

In this example, the fully encoded QR Packet would appear as so:

A113BD9004c175619882ef8485799f163bc906eddd562c02bc48975cfcf247http://xxx.yy/1?ip=17.29.42.137&os=0.1&osv=SP3

In this scenario, mobile asset application 22 may augment the asset datawith the mobile device data 26 to yield the following augmented data 28:

http://xxx.yy/1?ip=17.29.42.137&os=0.1&osv=SP3& when=3BE2&latitude=38.234231& longitude=34.234232& altitude-510&userId=user-1@xxx.yy& scanTime=1307126406& deviceString=Android2.3

Once augmented data 28 is generated, the augmented URL may be accessedby mobile device 10 and/or data center 60. In some embodiments,accessing the augmented URL will report information about asset 30 toasset manager 70. For example, the endpoint for the URL may decode theURL and enter the asset information into asset manager 70. As a resultof this process, asset manager 70 may learn information such as: (1)location of the asset, (2) the type of asset (e.g., for fundingpurposes), (3) when the asset was last used, and (4) operating system ofthe asset.

In a third example scenario, asset 30 is a printer, and a user is ableto print on the printer by scanning a QRCode associated with theprinter. In this example, the QRCode (communication tag 32) was notnecessarily generated by the printer (asset 30). In some embodiments,the QRCode may be attached to the printer or otherwise be physicallyassociated with the printer. In this example scenario, information 24includes:

[HEADER]

A—QRCode Format

1—Version

3BD9 (15327)—Days since EPOC 1970

004c (76)—Length of application data

[APPLICATION DATA]

printerIP=27.13.112.15 . . .

[ASSET DATA]

http://xxx.yy/1?assetID=13A13D17

Once augmented data 28 is generated from the asset data and mobiledevice data 26, the augmented URL may be accessed by mobile device 10and/or data center 60. In some embodiments, accessing the augmented URLwill report information about asset 30 to asset manager 70. As a resultof this process, asset manager 70 may learn information such as: (1)location of the printer, (2) who is using the printer, (3) when theprinter was last used, (4) model and make of the printer, and (5) thescanning device make and model.

In a fourth example scenario, asset 30 is a physical location within abuilding, such as a door. A user may be required to scan a QRCode(communication tag 32) before entering the physical location. In thisexample, the business application may determine whether the user isauthorized to access the physical location. In this example scenario,information 24 includes:

[HEADER]

A—QRCode Format

1—Version

3BD9 (15327)—Days since EPOC 1970

004c (76)—Length of application data

[APPLICATION DATA]

DoorID=12;resourceID=12123 . . .

[ASSET DATA]

http://xxx.yy/1?assetID=12123

In this example, the business application data also happens to identifyasset 12123. Once augmented data 28 is generated from the asset data andmobile device data 26, the augmented URL may be accessed by mobiledevice 10 and/or data center 60. As a result of this process, assetmanager 70 may learn information such as: (1) when the physical locationwas last accessed, (2) the mobile device scanning the QRCode, and (3)the person requesting access to the physical location.

In each of these four scenarios, communication tag 32 is a QRCode.Teachings of certain embodiments recognize, however, that other types ofcommunication tags may be used. In some embodiments, for example,communication tag 32 is a NFC device. Like QRCodes, NFC may be capableof transmitting both business application data and asset data.

Although communication tags such as QRCodes and NFC devices have largerstorage capacities than one-dimensional barcodes, the storage capacitiesof QRCodes and NFC devices are still limited. Thus, teachings of certainembodiments provide the capability to prioritize which information isincluded in communication tag 32.

The amount of available space for asset data depends on how much spaceis dedicated to business application data. If communication tag 32 islimited to 512 bytes of data, for example, asset data will be limited tothe following bytes: 379 bytes if 133 bytes are dedicated to businessapplication data; 34 bytes if 478 bytes are dedicated to businessapplication data; and 0 bytes if 534 bytes are dedicated to businessapplication data. In the last example, 0 bytes are available for assetdata because the business application data has exceeded the 512 bytesize constraint.

In addition to prioritizing between business application data and assetdata, teachings of certain embodiments provide the capability toprioritize which fields are included in asset data. Asset data mayinclude a variety of different fields, including, but not limited to:“assetId” (the asset identifier associated with a specific asset);“type” (type of asset, e.g., P=printer, D=desktop, L=laptop, M=mobiledevice); “IP” (the IP address associated with the asset, in 4 byte to 16byte form); “mac” (the mac address associated with an asset, in 6 byteform); “os” (operating system, e.g., 0=Windows, 0.0=Windows XP,0.1=Windows 2000, 0.2=Windows 2K3 Server, 0.3=Windows vista, 1=Unix,1.0=Linux, 1.1=BSD, 2=MacOSX); and “osv” (operating system version).

In one example embodiment, assetId is included in the asset data if thesize constraint has not been exceeded and the assetId is known. If thereis still room within the size constraint after assetId is included inthe asset data, the remaining fields may be included in the followingorder of priority: IP, type, mac, os, and osv.

FIG. 3 shows a method 300 for generating, scanning, and processingcommunication tags. At step 310, business application data is received.If the business application data exceeds the size constraints associatedwith the communication tag, then the communication tag is generatedwithout asset data at step 320. If the business application data doesnot exceed the size constraints associated with the communication tag,then the communication tag is generated with the asset data and thebusiness application data at step 330.

At step 340, the communication tag is scanned by a mobile device. Thebusiness application data is extracted from the communication tag andtransmitted to the business application at step 345. The asset data isextracted from the communication tag and augmented with mobile devicedata at step 350, and the resulting augmented data is transmitted to anasset manager at step 360. Modifications, additions, or omissions may bemade to the systems and apparatuses described herein without departingfrom the scope of the invention. The components of the systems andapparatuses may be integrated or separated. Moreover, the operations ofthe systems and apparatuses may be performed by more, fewer, or othercomponents. The methods may include more, fewer, or other steps.Additionally, steps may be performed in any suitable order.Additionally, operations of the systems and apparatuses may be performedusing any suitable logic. As used in this document, “each” refers toeach member of a set or each member of a subset of a set.

Although several embodiments have been illustrated and described indetail, it will be recognized that substitutions and alterations arepossible without departing from the spirit and scope of the presentinvention, as defined by the appended claims.

What is claimed is:
 1. A mobile device, comprising: a Quick Responsecode (QRCode) scanner operable to scan information from a QRCode createdby an asset, the information comprising: a header describing theinformation; a uniform resource locator (URL) containing assetidentification data uniquely identifying the asset that created theQRCode; and business application data not associated with the asset; amemory operable to store the information and mobile device dataassociated with the mobile device comprising data: identifying alocation of the mobile device, identifying when the QRCode is scanned,and identifying a user associated with the mobile device; a processor,communicatively coupled to the memory, the processor configured to:extract the business application data from the information scanned fromthe QRCode; provide the business application data to a businessapplication; extract the URL from the information scanned from theQRCode; insert the mobile device data identifying the location of themobile device, when the QRCode is scanned, and the user associated withthe mobile device into the URL to yield an augmented URL; and access anendpoint for the augmented URL, the endpoint configured to: retrieve,from the augmented URL, the asset identification data uniquelyidentifying the asset that created the QRCode; and track placement ofthe asset that created the QRCode based on the location of the mobiledevice from the mobile device data in the augmented URL.
 2. A device,comprising: an interface configured to scan information from acommunication tag created by an asset, the information comprising:business application data; and a uniform resource locator (URL)containing asset identification data uniquely identifying the asset thatcreated the communication tag; a memory operable to store theinformation and device data associated with the device, the device datacomprising data identifying a location of the device; and a processor,communicatively coupled to the memory, the processor configured to:extract the business application data from the information scanned fromthe communication tag; extract the asset identification data from theinformation scanned from the communication tag; insert the device datainto the URL to yield an augmented URL; and access an endpoint for theaugmented URL, the endpoint configured to: retrieve, from the augmentedURL, the asset identification data uniquely identifying the asset thatcreated the communication tag; and track placement of the asset thatcreated the communication tag based on the location of the device fromthe device data in the augmented URL.
 3. The device of claim 2, wherein:the processor is configured to augment the asset identification datawith the device data to yield augmented data.
 4. The device of claim 3,wherein: augmenting the asset identification data with the device datacomprises inserting the data identifying the location of the device intothe asset identification data to yield the augmented data.
 5. The deviceof claim 3, wherein: the device data comprises data identifying when thecommunication tag is scanned; and augmenting the asset identificationdata with the device data comprises inserting the data identifying whenthe communication tag is scanned into the asset identification data toyield the augmented data.
 6. The device of claim 3, wherein: the devicedata comprises data uniquely identifying the device or a user associatedwith the device; and augmenting the asset identification data with thedevice data comprises inserting the data identifying the device or auser associated with the device into the asset identification data toyield the augmented data.
 7. The device of claim 2, wherein the devicedata is inserted into a query string of the URL to yield the augmentedURL, and wherein the endpoint is further configured to retrieve thedevice data from the query string of the augmented URL.
 8. The device ofclaim 6, the processor being further configured to transmit the URL toan asset manager.
 9. The device of claim 2, wherein: the communicationtag is a Quick Response code (QRCode); and the interface is configuredto scan the QRCode.
 10. The device of claim 2, wherein the interface isconfigured to scan the communication tag using near-field communication.11. A method for managing assets in a business environment, comprising:scanning information from a communication tag created by an asset, theinformation comprising: business application data; and a uniformresource locator (URL) containing asset identification data uniquelyidentifying the asset that created the communication tag; extracting thebusiness application data from the information scanned from thecommunication tag; providing the business application data to a businessapplication; extracting the asset identification data from theinformation scanned from the communication tag; inserting mobile devicedata associated with a mobile device into the URL to yield an augmentedURL, the mobile device data comprising data identifying a location ofthe mobile device; and accessing an endpoint for the augmented URL, theendpoint configured to: retrieve the asset identification data uniquelyidentifying the asset that created the communication tag; and trackplacement of the asset that created the communication tag based on thelocation of the mobile device from the mobile device data in theaugmented URL.
 12. The method of claim 11, further comprising augmentingthe asset identification data with the mobile device data to yieldaugmented data.
 13. The method of claim 12, wherein: augmenting theasset identification data with the mobile device data comprisesinserting the data identifying the location of the mobile device intothe asset identification data to yield the augmented data.
 14. Themethod of claim 12, wherein: the mobile device data comprises dataidentifying when the communication tag is scanned; and augmenting theasset identification data with the mobile device data comprisesinserting the data identifying when the communication tag is scannedinto the asset identification data to yield the augmented data.
 15. Themethod of claim 12, wherein: the mobile device data comprises datauniquely identifying the mobile device or a user associated with themobile device; and augmenting the asset identification data with themobile device data comprises inserting the data identifying the mobiledevice or a user associated with the mobile device into the assetidentification data to yield the augmented data.
 16. The method of claim11, wherein the mobile device data is inserted into a query string ofthe URL to yield the augmented URL, and wherein the endpoint is furtherconfigured to retrieve the mobile device data from the query string ofthe augmented URL.
 17. The method of claim 12, further comprisingtransmitting the URL to an asset manager.
 18. The method of claim 11,wherein: the communication tag is a Quick Response code (QRCode); andthe interface is configured to scan the QRCode.